ci: raise coverage unit-test job timeout to 30 minutes - #1626
Merged
Conversation
The unit test job that runs with coverage instrumentation can exceed the 20-minute timeout. Give it 30 minutes while leaving the other unit jobs at 20.
Coverage report
This PR does not seem to contain any modification to coverable code. |
jprakash-db
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The unit test job in
main.ymlruns the suite with coverage instrumentation (test:unit-with-cov), which is slower than the other unit jobs and can exceed the shared 20-minute timeout.This raises the timeout for that job to 30 minutes, leaving the other unit jobs (including
main-min-deps.yml) at 20.Example timeout: https://github.com/databricks/dbt-databricks/actions/runs/31261109055/job/93111926509?pr=1621
Checklist